Print

This update requires you to make changes to the following files:

• /Web.config
• /App_Config/Commands.config
• /App_Config/Include/Sitecore.Buckets.config

Depending on search provider you should also update appropriate files below:

• Sitecore solution configured to use Lucene:
  • /App_Config/Include/Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config
• Sitecore solution configured to use Solr:
  • /App_Config/Include/Sitecore.ContentSearch.Solr.Indexes.config

The clean configuration files for Sitecore CMS and DMS 7.0 rev. 131127 can be downloaded using the following links:

• Web.config
• Commands.config
• Sitecore.Buckets.config 
• Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config 
• Sitecore.ContentSearch.Solr.Indexes.config 
  

Changes to the Web.config file 
The following changes have been made to the Web.config file of Sitecore CMS 7.0 rev. 131127 (Update-3) as compared to the Web.config file of Sitecore CMS 7.0 rev. 130918 (Update-2):

1. In the <publish> pipeline, add a new processor of type RaiseQueuedEvents between processors of type AddItemsToQueue and ProcessQueue:
   <publish help="Processors should derive from Sitecore.Publishing.Pipelines.Publish.PublishProcessor">
     <processor type="Sitecore.Publishing.Pipelines.Publish.AddLanguagesToQueue, Sitecore.Kernel"/>
     <processor type="Sitecore.Publishing.Pipelines.Publish.AddItemsToQueue, Sitecore.Kernel"/>
     <processor type="Sitecore.Publishing.Pipelines.Publish.RaiseQueuedEvents, Sitecore.Kernel"/>
     <processor type="Sitecore.Publishing.Pipelines.Publish.ProcessQueue, Sitecore.Kernel"/>
   </publish>
   

Changes to the Commands.config file 

The following changes have been made to the Commands.config file of Sitecore CMS 7.0 rev. 131127 (Update-3) as compared to the Commands.config file of Sitecore CMS 7.0 rev. 130918 (Update-2):

1. Add the following command after the "contenteditor:incrementmark" command:
   <command name="contenteditor:navigate" type="Sitecore.Shell.Framework.Commands.ContentEditor.Navigate,Sitecore.Kernel" />
   

Changes to the Sitecore.Buckets.config

The following changes have been made to the Sitecore.Buckets.config file of Sitecore CMS 7.0 rev. 131127 (Update-3) as compared to the Sitecore.Buckets.config file of Sitecore CMS 7.0 rev. 130918 (Update-2):

1. In the <buckets.cloneItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
   <!-- CLONE ITEM INTO BUCKET PIPELINE
        Pipeline for cloning items into an item bucket.
        Arguments : (Item) Source, (Item) Target, (bool) Whether or not cloning was successful, (bool) Deep check.
   -->
   <buckets.cloneItemIntoBucket>
     <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CloneItem.RunCloning, Sitecore.Buckets"/>
     <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CloneItem.ProcessParentReference, Sitecore.Buckets"/>
   </buckets.cloneItemIntoBucket>
   
2. In the <buckets.copyItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
   
   <!-- COPY ITEM INTO BUCKET PIPELINE
        Pipeline for copying items into an item bucket.
        Arguments : (Item) The item to add a search tab to. (bool) Whether the tab was added or not.
   -->
   <buckets.copyItemIntoBucket>
     <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CopyItem.RunCopying, Sitecore.Buckets"/>
     <processor type="Sitecore.Buckets.Pipelines.ItemOperations.CopyItem.ProcessParentReference, Sitecore.Buckets"/>
   </buckets.copyItemIntoBucket>
   
3. In the <buckets.moveItemIntoBucket> pipeline, add a new processor of type ProcessParentReference after the existing processor:
         <!-- MOVE ITEM INTO BUCKET PIPELINE
                    Pipeline for moving items into or out of an item bucket. This pipeline also makes sure that the item being moved is “bucketable”. If it is bucketable, it is automatically bucketed after it has been moved.
                    Arguments : (Item) The item being moved. (bool) Whether the item was moved successfully or not.
               -->
               <buckets.moveItemIntoBucket>
                 <processor type="Sitecore.Buckets.Pipelines.ItemOperations.MoveItem.RunMoving, Sitecore.Buckets"/>
                 <processor type="Sitecore.Buckets.Pipelines.ItemOperations.MoveItem.ProcessParentReference, Sitecore.Buckets"/>
         </buckets.moveItemIntoBucket>
   
4. In the <pipelines> section, add the following pipeline:
   <!-- EXPAND ID-BASED SEARCH FILTERS
        Sitecore executes this pipeline for search filters when their Client Side Hook is set to "id". To display a user-friendly item name
        in the UI, the ExpandIds processor replaces "<ID>" with "<Item Display Name>|<ID>" in these search filters.
   -->
   <buckets.expandIdBasedSearchFilters>
     <processor type="Sitecore.Buckets.Pipelines.UI.ExpandIdBasedSearchFilters.ExpandIds, Sitecore.Buckets"/>
   </buckets.expandIdBasedSearchFilters>
   
5. In the <settings> section, remove the "BucketConfiguration.EnableSearchTips" setting:
   <!-- ENABLE SEARCH TIPS IN UI
        This setting globally disables tips for every user. If you want to disable tips at the user level, use the User Manager.
   -->
   <setting name="BucketConfiguration.EnableSearchTips" value="true"/>
   

Changes to the Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file

The following changes have been made to the Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config file of Sitecore CMS 7.0 rev. 131127 (Update-3) as compared to the Sitecore.ContentSearch.Lucene.DefaultIndexConfiguration.config of Sitecore CMS 7.0 rev. 130918 (Update-2):

1. In the <fieldMap><fieldNames> section, add a new field mapping for the "site" computed field (you can add it at any place in the section, but in a clean Sitecore installation the new node is placed between the "_group" and "_latestversion" nodes):
   <field fieldName="site" storageType="YES" indexType="TOKENIZED" vectorType="NO" boost="1f" type="System.String" settingType="Sitecore.ContentSearch.LuceneProvider.LuceneSearchFieldConfiguration, Sitecore.ContentSearch.LuceneProvider">
     <analyzer type="Sitecore.ContentSearch.LuceneProvider.Analyzers.LowerCaseKeywordAnalyzer, Sitecore.ContentSearch.LuceneProvider" />
   </field>
   

2. In the <defaultIndexConfiguration> section, add a new <mediaIndexing> node:

   <!-- MEDIA ITEM CONTENT EXTRACTOR FILE MAPPING
        This map allows you to specify the extensions and mimetypes that we will pass through to the IFilters on your machine so they can be indexed.
        We also allow you to include all files or exclude all files and leave it to the IFilters to control what is and is not indexed.
   -->
   <mediaIndexing hint="raw:AddMediaIndexingMap">
     <mimeTypes>
       <excludes>
         <mimeType>*</mimeType>
       </excludes>
       <includes>
         <mimeType>application/pdf</mimeType>
         <mimeType type="Sitecore.ContentSearch.ComputedFields.MediaItemHtmlTextExtractor, Sitecore.ContentSearch">text/html</mimeType>
         <mimeType>text/plain</mimeType>
       </includes>
     </mimeTypes>
     <extensions>
       <excludes>
         <extension>*</extension>
       </excludes>
       <includes>
         <extension>rtf</extension>
         <extension>odt</extension>
         <extension>doc</extension>
         <extension>dot</extension>
         <extension>docx</extension>
         <extension>dotx</extension>
         <extension>docm</extension>
         <extension>dotm</extension>
         <extension>xls</extension>
         <extension>xlt</extension>
         <extension>xla</extension>
         <extension>xlsx</extension>
         <extension>xlsm</extension>
         <extension>xltm</extension>
         <extension>xlam</extension>
         <extension>xlsb</extension>
         <extension>ppt</extension>
         <extension>pot</extension>
         <extension>pps</extension>
         <extension>ppa</extension>
         <extension>pptx</extension>
         <extension>potx</extension>
         <extension>ppsx</extension>
         <extension>ppam</extension>
         <extension>pptm</extension>
         <extension>potm</extension>
         <extension>ppsm</extension>
       </includes>
     </extensions>
   </mediaIndexing>
   
3. In the <defaultIndexConfiguration> section, add a new <documentBuilderType> node:
   <!-- DOCUMENT BUILDER
        Allows you to override the document builder. The document builder class processes all the fields in the Sitecore items and prepares
        the data for storage in the index.
        You can override the document builder to modify how the data is prepared, and to apply any additional logic that you may require.
   -->
   <documentBuilderType>Sitecore.ContentSearch.LuceneProvider.LuceneDocumentBuilder, Sitecore.ContentSearch.LuceneProvider</documentBuilderType>
   
4. Optional: Replace the description of the computed index fields:
   <!-- COMPUTED INDEX FIELDS
        This setting allows you to add fields to the index that contain computed values that are based on the item that is being indexed.
   -->
   
   with
   
   <!-- COMPUTED INDEX FIELDS
        This setting allows you to add fields to the index that contain values that are computed for the item that is being indexed.
        You can specify the storageType and indextype for each computed index field in the <fieldMap><fieldNames> section.
   -->
   
5. Optional: Remove all "storageType" and "indexType" attributes from the <field hint="raw:AddComputedIndexField"> section, since these attributes are not used by the system. In a clean Sitecore installation, the section now looks like this:
   <fields hint="raw:AddComputedIndexField">
     <field fieldName="_content">
     Sitecore.ContentSearch.ComputedFields.MediaItemContentExtractor,Sitecore.ContentSearch
     </field>
     <field fieldName="calculateddimension">
     Sitecore.ContentSearch.ComputedFields.CalculatedDimension,Sitecore.ContentSearch
     </field>
     <field fieldName="daterange_month">
     Sitecore.ContentSearch.ComputedFields.DateRangeMonthFacet,Sitecore.ContentSearch
     </field>
     <field fieldName="daterange_week">
     Sitecore.ContentSearch.ComputedFields.DateRangeWeekFacet,Sitecore.ContentSearch
     </field>
     <field fieldName="daterange_year">
     Sitecore.ContentSearch.ComputedFields.DateRangeYearFacet,Sitecore.ContentSearch
     </field>
     <field fieldName="istemplate">
     Sitecore.ContentSearch.ComputedFields.IsTemplate,Sitecore.ContentSearch
     </field>
     <field fieldName="lock">
     Sitecore.ContentSearch.ComputedFields.IsLocked,Sitecore.ContentSearch
     </field>
     <field fieldName="parsedcreatedby">
     Sitecore.ContentSearch.ComputedFields.ParsedCreatedBy,Sitecore.ContentSearch
     </field>
     <field fieldName="parsedupdatedby">
     Sitecore.ContentSearch.ComputedFields.ParsedUpdatedBy,Sitecore.ContentSearch
     </field>
     <field fieldName="parsedlanguage">
     Sitecore.ContentSearch.ComputedFields.ParsedLanguage,Sitecore.ContentSearch
     </field>
     <field fieldName="site">
     Sitecore.ContentSearch.ComputedFields.Site,Sitecore.ContentSearch
     </field>
     <field fieldName="sizerange">
     Sitecore.ContentSearch.ComputedFields.FileSizeGrouping,Sitecore.ContentSearch
     </field>
     <field fieldName="version">
     Sitecore.ContentSearch.ComputedFields.StoreVersionTermVector,Sitecore.ContentSearch
     </field>
     <field fieldName="urllink">
     Sitecore.ContentSearch.ComputedFields.UrlLink,Sitecore.ContentSearch
     </field>
     <field fieldName="isbucket_text">
     Sitecore.ContentSearch.ComputedFields.IsBucket,Sitecore.ContentSearch
     </field>
     <!-- Disabled for speed of indexing. Enable if you would like to query by the fields below -->
     <!--<field fieldName="_isclone">
     Sitecore.ContentSearch.ComputedFields.IsClone,Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="_links">
     Sitecore.ContentSearch.ComputedFields.ItemLinks, Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="_templates">
     Sitecore.ContentSearch.ComputedFields.AllTemplates, Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="hasactivetest">
     Sitecore.ContentSearch.ComputedFields.IsBeingTested,Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="hasclones">
     Sitecore.ContentSearch.ComputedFields.HasClones,Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="haspublishingrestrictions">
     Sitecore.ContentSearch.ComputedFields.HasPublishingRestrictions,Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="isinworkflow">
     Sitecore.ContentSearch.ComputedFields.IsItemInWorkflow,Sitecore.ContentSearch
     </field>-->
     <!--<field fieldName="persona">
     Sitecore.ContentSearch.ComputedFields.PersonaMatch,Sitecore.ContentSearch
     </field>-->
   </fields>
   

Changes to the Sitecore.ContentSearch.Solr.Indexes.config file

The following changes have been made to the Sitecore.ContentSearch.Solr.Indexes.config file of Sitecore CMS 7.0 rev. 131127 (Update-3) as compared to the Sitecore.ContentSearch.Solr.Indexes.config of Sitecore CMS 7.0 rev. 130918 (Update-2):

1. In the <defaultIndexConfiguration> section, add a new <mediaIndexing> node:
   <!-- MEDIA ITEM CONTENT EXTRACTOR FILE MAPPING
        This map allows you to specify the extensions and mimetypes that we will pass through to the IFilters on your machine so they can be indexed.
        We also allow you to include all files or exclude all files and leave it to the IFilters to control what is and is not indexed.
   -->
   <mediaIndexing hint="raw:AddMediaIndexingMap">
     <mimeTypes>
       <excludes>
         <mimeType>*</mimeType>
       </excludes>
       <includes>
         <mimeType>application/pdf</mimeType>
         <mimeType type="Sitecore.ContentSearch.ComputedFields.MediaItemHtmlTextExtractor, Sitecore.ContentSearch">text/html</mimeType>
         <mimeType>text/plain</mimeType>
       </includes>
     </mimeTypes>
     <extensions>
       <excludes>
         <extension>*</extension>
       </excludes>
       <includes>
         <extension>rtf</extension>
         <extension>odt</extension>
         <extension>doc</extension>
         <extension>dot</extension>
         <extension>docx</extension>
         <extension>dotx</extension>
         <extension>docm</extension>
         <extension>dotm</extension>
         <extension>xls</extension>
         <extension>xlt</extension>
         <extension>xla</extension>
         <extension>xlsx</extension>
         <extension>xlsm</extension>
         <extension>xltm</extension>
         <extension>xlam</extension>
         <extension>xlsb</extension>
         <extension>ppt</extension>
         <extension>pot</extension>
         <extension>pps</extension>
         <extension>ppa</extension>
         <extension>pptx</extension>
         <extension>potx</extension>
         <extension>ppsx</extension>
         <extension>ppam</extension>
         <extension>pptm</extension>
         <extension>potm</extension>
         <extension>ppsm</extension>
       </includes>
     </extensions>
   </mediaIndexing>
   
2. In the <defaultIndexConfiguration> section, add a new <documentBuilderType> node:
   <!-- DOCUMENT BUILDER
        Allows you to override the document builder. The document builder class processes all the fields in the Sitecore items and prepares
        the data for storage in the index.
        You can override the document builder to modify how the data is prepared, and to apply any additional logic that you may require.
   -->
   <documentBuilderType>Sitecore.ContentSearch.SolrProvider.SolrDocumentBuilder, Sitecore.ContentSearch.SolrProvider</documentBuilderType>
   
3. Optional: Replace the description of the computed index fields:
   <!-- COMPUTED INDEX FIELDS
        This setting allows you to add fields to the index that contain computed values that are based on the item that is being indexed.
   -->
   
   with
   
   <!-- COMPUTED INDEX FIELDS
        This setting allows you to add fields to the index that contain values that are computed for the item that is being indexed.
        You can specify the storageType and indextype for each computed index field in the <fieldMap><fieldNames> section.
   -->